Versions:

9.3.3
9.3.2
9.3.1
9.3.0
9.2.4
9.2.3
9.2.2
9.2.1
9.2.0
9.1.5
9.1.4
9.1.3
9.1.1
9.1.0
9.0.4
9.0.3
9.0.2
9.0.1
9.0.0

Elastic’s Beats Heartbeat 9.3.3 is a lightweight, open-source uptime monitor designed to sit alongside the Elastic Stack and continuously probe remote services for availability. Operating as one of the 19 maintained releases in the Beats family, Heartbeat sends scheduled PING, TCP, TLS, HTTP, or ICMP packets to any endpoint—whether a public website, internal API gateway, or containerized micro-service—and instantly forwards the resulting latency and up/down state to Elasticsearch or Logstash for correlation, alerting, and long-term trending in Kibana. The agent’s declarative YAML syntax lets operators define multiple monitors with custom intervals, timeouts, expected status codes, certificate expiry checks, and multi-step journey scripting, so the same binary can watch a handful of legacy hosts or thousands of globally distributed cloud resources without additional infrastructure. Typical deployments include DevOps teams embedding Heartbeat in CI pipelines to gate production releases on service health, network administrators verifying WAN link stability across branch offices, and SaaS providers documenting SLA compliance for customers. Because the executable is cross-platform and self-contained, it is equally at home running as a Windows service, a Linux systemd unit, or a Kubernetes DaemonSet, consuming only a few megabytes of RAM while emitting structured JSON that enriches observability data with geo-location, cloud metadata, and container labels. Configuration reloading and external secrets support allow zero-downtime updates, while built-in back-pressure protection prevents monitoring traffic from overwhelming already strained targets. The software is available for free on get.nero.com, with downloads provided via trusted Windows package sources such as winget, always delivering the latest version and supporting batch installation of multiple applications.

Tags:

Beats heartbeat